?2012 p&e microcomputer systems, inc. kinetis, qorivva, and coldfi re are registered trademarks of freescale semiconductor, inc. the power architecture wordmark and related marks ar e trademarks and service marks licensed by power.org. p&e microcomputer systems, inc. www.pemicro.com technical summary for usb multilink universal, rev. b ( part# usb-ml-universal) and usb multilink universal fx , rev. a ( part# usb-ml-universal-fx) support for freescale kinetis ? qorivva ? mpc5xxx coldfire ? v1/coldfire+ v1 coldfire v2-4 px series hcs08 rs08 hc(s)12(x) s12z dsc hc16/683xx (fx only) document# pe4576, version 1.01 1. introduction 2. usage 3. driver installation 4. connecting to the target 5. troubleshooting - startup reset sequence 6. firmware updates/architecture selection 7. interface libraries 8. compatible software 9. transition to production programming 1 introduction the usb multilink universal and universal fx are all- in one debug interfaces which accelerate the debug and flash pr ogramming process, saving valuable development time. both multilinks provide access to debug modes on a wide range of free scale microcontroller families by communicating between the target device and a laptop/pc via the target?s standard debug header and the laptop/pc?s usb port. fx note: in addition, the usb multilink universal fx offers up to 10x faster download speeds and can provide target power. each of the supported families of freescale microcontrollers are represented by headers loca ted inside the unit. the headers for ports a-d & port h (fx only) are dual-row with a .100? pitch, and the headers for ports f-g are dual-row with a .050? pitch. the pin-outs for these connections and the fa milies that they support are shown below. port e, the 16-pin jtag/cop connector, is not currently supported. universal/universal fx pin-outs, ports a-d usb multilink universal & usb multilink universal fx
usb multilink universal & usb multilin k universal fx - technical summary universal/universal fx pin-outs, ports f-h the user can take advantage of debug modes to halt normal proc essor execution and use a computer to control the processor. the user can then directly control the targ et's execution, read/write registers and memory values, debug code on the processor, and program internal or exte rnal flash memory devices. fx note: the usb multilink universal fx is capable of providing power (5v or 3.3v) directly to the target processor via the tvcc pin. this removes the need for an external powe r supply for systems requiring 200ma of current or less. 2 usage the usb multilink universal and universal fx can communicate wi th kinetis (including l-seri es devices), qorivva mpc5xxx, coldfire v1/v2/v3/v4, power architecture px series, rs08, hcs08, hc(s)12(x), s12z, dsc, and hc16/683xx (fx only) microprocessors by connecting a ribbon cable between the target's debug header and one of the multiple ports on the multilink. do not attempt to use multiple ports at once, as this ma y damage both the target processors as well as the multilink. the usb multilink universal and universal fx interfaces will work with targets whose pr ocessor power supply is in the range of 1.8v to 5v. on the universal fx, if the user wishe s to provide power to the target, the jp10 jumper (fx only) is used to enable this option and select the voltage. a shunt at posi tion 1-2 enables 5v, while a shunt at pos ition 2-3 enables 3.3v. the usb multilink universal and universal fx have a female type b usb connector. use a type a to type b male-to-male usb cable to connect the interface to the pc. universal/universal fx header layout (pin 1 highlighted) there are two leds on the multilink interfac e. the blue led indicates that the interface is powered and running. the yellow led indicates that target power has been detected. note: if connecting to a coldfire v2-4 processor whic h requires synchronous communication, such as the mcf5272 and mcf5206(e), a cable-cf-adapter (sold separately) is required. note: to avoid improper connections, the red stripe of th e ribbon cable should always be oriented towards pin 1, both on the multilink port and the target processor header. the usb multilink universal and universal fx are usb devices. if a usb hub is used, it must be a self-powered hub (i.e. with its own power supply). by default, the usb protocol used is usb 2.0.
usb multilink universal & usb multilin k universal fx - technical summary 3 driver installation before connecting the multilink to the pc, the appropriate driv ers need to be installed on the pc. the multilink drivers are supported on windows xp, 2000, 2003, vista, and 7. these drivers are automatically installed when installing freescale?s codewarrior or any of p&e?s recent softwa re development packages. if you have insta lled a recent versi on of these then the instructions for manual installation that follow are not ne cessary. however, windows 7 users who are installing software distributed before december 28, 2009 will need to obtain the late st version of the drivers and install them manually. a copy of the driver installation program may be downloaded from the ?dow nloads? section of p&e?s ?support center? located at http:// www.pemicro.com. if you are using third-part y software, make sure you have a version which supports your specific interface (universal/fx). once you have obtained the latest version of th e driver installation program, please use the instructions below to manually install the drivers. when the cable is plugged in, the operating system should indicate that it has found a driver for the attached interface. foll ow the instructions in the ?found new hardware wizard? dial og for having windows automatically install the driver. if you connected the multilink interface prior to installing the drivers, win dows will not have been able to find the appropria te driver and may have disabled the device. if you unplug the device and then plug it in again, windows will automatically disable it even if you have installed the drivers. to force windows to attempt to load the driver again, perform the following steps wh ile the multilink interface is plugged into the computer: 1. open the control panel: start button [ ->se ttings ] ->control panel. (you will not ne ed to select ?settings? on vista and win- dows 7). 2. double click the ?system? icon. (windows 7: ?system and security?) 3. select the ?hardware? tab. (windows 7: ?hardw are and sound?, windows vista: skip this step) 4. click the ?device manager? button. (windows 7: ?devices and printers -> device manager?) 5. the ?usb multilink 2.0? device will be shown with an excl amation point next to it. double-click this device. 6. click the ?reinstall driver?? button and follow the dialog instru ctions to have windows automatically install the driver. (win- dows 7: first click the ?driver? tab, then select ?update driver...?) 7. if the hardware still has a yellow exclamation mark next to it , right click on it and select uninstall. the usb multilink shoul d disappear from the list. unplug the usb multilink and then plug it into the pc again. a new hardware found dialog will pop up; follow the dialog instructions and hav e windows automatically install the driver. 4 connecting to the target the following is the proper connection sequence to connec t the pc to the target system via the multilink interface: 1. make sure the target power is off and the usb multilink universa l or universal fx is not connect ed to either the target or the pc 2. open the multilink and connect a ribbon c able from the correct multilink port to the target. make sure that the ribbon cable is plugged into the target with the proper orientat ion. pin 1 is indicated by a 1 next to the port. 3. connect the multilink to the pc via a usb cable. the blue led on the multilink should illuminate. 4. turn the target power on. the yellow led on the multilink should illuminate. before disconnecting the setup, turn the target power off. 5 troubleshooting - startup reset sequence note that if the multilink does not enter debug mode, the program issues the error message ?cannot enter background mode.? if you receive this message you should check your hardware with a scope, logic analyzer or logic probe. first check for power on, then check to make sure the processor oscillator is running. fi nally, look for the startup sequence for your microprocessor tha t is listed below. port a ? jtag/once ? qorivva mpc5x xx, power architecture px series, dsc a. reset (pin-9) is driv en low (to processor). b. activity appears on tck (pin-5), tdi (pin-1) and td o (pin-3). (pc software in structs the processor to enable debug mode). c. reset (pin-9) is released by the interface and will go high. d. activity appears on tck (pin-5), tdi (pin-1) and tdo (pin-3). (debug activity). ports b, f, g ? arm jtag - kinetis a. reset is driven low (to processor). b. activity appears on tck, tdi and tdo (pc software instructs the processor to enable debug mode). c. reset is released by the interface and will go high. d. activity appears on tck , tdi and tdo (debug activity).
usb multilink universal & usb multilin k universal fx - technical summary port c ? bdm rs08, hcs08, s12z, coldfire v1 a. debug activity is seen on bkgd (pin-1). hc(s)12(x) a. bkgd (pin-1) and reset (pin-4) are pulled low by the interface. b. after 5 millisec onds, reset (pin-4) is released and goes high. c. after 10 milliseconds, bkgd (pin -1) is released and goes high. d. after 20 more milliseconds, debug activity is seen on bkgd (pin-1). port d ? coldfire v2/v3/v4 a. bkpt (pin-2), dsi (pin-8), and dscl k (pin-4) signals are driven low. b. reset (pin-7) is driven low fo r 20+ milliseconds and released. c. after reset is rele ased and if the proc essor has correctly en tered backgrou nd mode, the pst0 (pin-15), pst1 (pin-14), pst2 (pin-13) and pst3 (pin-12) lines should all be driven high by the processor. d. activity (changing signals) is seen on the dsi, ds o, and dsclk signals. the ac tivity on the dsclk and dsi lines is generated by the pc and the activity on the dso line is generated by the processor. port e ? jtag/cop (not yet supported) port h - hc16/683xx (fx only) a. bkpt/dsclk is pulled low (to processor). b. delay ~1ms. c. reset is pulled low (to processor). d. delay ~20ms. e. reset is released (tri stat e, should be pulled up on target). f. wait for freeze (out of processor). g. shifting activity appears on dsclk, dsi and dso. 6 firmware updates/architecture selection the multilink universal and universal fx use firmware updates to change between modes of operation to support different families of freescale microcontrollers. olde r versions of p&e's software and third-part y software are not able to automatically configure these multilinks when the target is switched to a different family of micr ocontrollers. if you are not using the late st version of p&e software, please contact us to determine if you are eligible for a disco unted upgrade to the latest version of y our software. you may also download a manual configuration utility for the multilink from the support center or corresponding product page on our website: http://www.pemicro.com/s upport/downloads_find.cfm 7 interface libraries p&e produces a set of interface libraries wh ich allow the user to directly control t he usb multilink univer sal or universal fx from any windows development environment which can interact with a dll. the interface libraries come with examples for controlling the multilink interface from mi crosoft visual c as well as borland delphi . more details can be found on the interfa ce libraries page on the p&e website: http://www.pemicro.com /products/product_processor.cfm?category=9 8 compatible software the usb multilink universal and universal fx are supported by rec ent versions of freescale?s codewarrior (10.x) as well as third-party toolchains from iar, keil, cosmic, and ment.or graphics. it is recommended that you check with the vendor regarding support for your specific part. information on compatible p&e software can be found in the ?pr oducts? section of www.pemicro.com. 9 transition to production programming the usb multilink universal and universal fx are intended for development and are not designed to accomodate the demands of production programming. however, p&e?s cyclone programmers are s pecifically engineered to withstand the rigors of a pr oduction environment and will provide a seamless transition from the multilink. more information is available online at pemicro.com/cyclonepro and pemicro.com/cyclonemax. cyclone pro & cyclone max
|
